Non-cellular link integration with cellular networks

ABSTRACT

Improved non-cellular (e.g., Wi-Fi) link integration with a cellular (e.g., LTE) network is described. The improved link integration can relate to utilizing an eNodeB device (e.g., residing in a radio access network portion of a cellular network) as an anchor point rather than a packet data network gateway device (e.g., residing in a core network portion of the cellular network) utilized by other approaches. The improved link integration can maintain full compliance with or support for other approaches, and can reduce signaling overhead, simplify quality-of-service management, and/or provide a more rapid reaction to changes of access, particularly in cases where the eNodeB device and a non-cellular access point device are co-located.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims priority to each of,U.S. patent application Ser. No. 15/005,585 (now U.S. Pat. No.9,544,843), filed on Jan. 25, 2016, entitled “NON-CELLULAR LINKINTEGRATION WITH CELLULAR NETWORKS”, which is a continuation of U.S.patent application Ser. No. 14/042,064 (now U.S. Pat. No. 9,277,580),filed on Sep. 30, 2013, entitled “NON-CELLULAR LINK INTEGRATION WITHCELLULAR NETWORKS.” The entireties of the above noted applications areincorporated herein by reference.

TECHNICAL FIELD

The present application relates generally to integrating non-cellularcommunication with a cellular communication network.

BACKGROUND

Third generation partnership project (3GPP) standards define hownon-3GPP access can be integrated into the long term evolution (LTE)cellular infrastructure in specification TS 23.402 and severaladditional documents. A number of architectural designs are specifiedfor different application situations such as roaming vs. non-roaming,local breakout vs. home-routed, etc. However, such documents share thesame fundamental approach. In this regard, a mobile device or other userequipment (UE) attached to a non-3GPP access network forms a “tunnel” toa packet data network gateway (PGW) in the evolved packet core of theLTE cellular infrastructure over the non-3GPP link and the associatedaccess network, and uses the tunnel at the PGW as an integration anchorpoint.

BRIEF DESCRIPTION OF THE DRAWINGS

Numerous aspects, embodiments, objects and advantages of the presentinvention will be apparent upon consideration of the following detaileddescription, taken in conjunction with the accompanying drawings, inwhich like reference characters refer to like parts throughout, and inwhich:

FIG. 1 illustrates a block diagram of an example mobile device and anexample eNodeB device that can provide for non-cellular link integrationwith cellular networks in accordance with certain embodiments of thisdisclosure;

FIG. 2 illustrates a block diagram of an example integrated network inaccordance with certain embodiments of this disclosure;

FIG. 3 illustrates a block diagram of an example system according to anembedded co-location embodiment in accordance with certain embodimentsof this disclosure;

FIG. 4 illustrates a block diagram of an example system according to atunneled co-location embodiment in accordance with certain embodimentsof this disclosure;

FIG. 5A illustrates an example diagram that illustrates various exampleLTE bearers in accordance with certain embodiments of this disclosure;

FIG. 5B illustrates an example diagram that illustrates an example setof links between the mobile device and the access point device inaccordance with certain embodiments of this disclosure;

FIG. 5C illustrates an example diagram that illustrates an example setof virtual tunnels between the mobile device and the eNodeB device inaccordance with certain embodiments of this disclosure;

FIG. 6 illustrates a block diagram of an example system that can providefor additional aspects, features, or detail in connection withintegrating non-LTE links with an LTE network in accordance with certainembodiments of this disclosure;

FIG. 7A is an illustration of a protocol stack diagram that provides foran embedded co-location embodiment in which non-3GPP link layer framescarry data in accordance with certain embodiments of this disclosure;

FIG. 7B is an illustration of a protocol stack diagram that provides foran embedded co-location embodiment in which data is encapsulated byanother layer of IP header in accordance with certain embodiments ofthis disclosure;

FIG. 8A is an illustration of a protocol stack diagram that provides fora tunneled co-location embodiment in which a non-3GPP bridging accesspoint resides on a same LAN as the eNodeB device in accordance withcertain embodiments of this disclosure;

FIG. 8B is an illustration of a protocol stack diagram that provides fortunneled co-location embodiment in which the non-3GPP bridging accesspoint resides on a higher IP layer as part of a routing function inaccordance with certain embodiments of this disclosure;

FIG. 9 illustrates an example methodology that can provide forintegrating non-LTE links with LTE networks in accordance with certainembodiments of this disclosure;

FIG. 10 illustrates an example methodology that can provide for variousexample techniques associated with determining that the access pointdevice and the eNodeB device are co-located in accordance with certainembodiments of this disclosure;

FIG. 11 illustrates an example methodology that can provide foradditional features or aspects in connection with integrating non-LTElinks with LTE networks in accordance with certain embodiments of thisdisclosure;

FIG. 12 a first example of a wireless communications environment withassociated components that can be operable to execute certainembodiments of this disclosure;

FIG. 13 a second example of a wireless communications environment withassociated components that can be operable to execute certainembodiments of this disclosure; and

FIG. 14 illustrates an example block diagram of a computer operable toexecute certain embodiments of this disclosure.

DETAILED DESCRIPTION

In response to increased demand for capacity, communication networkcarriers are reducing cell sizes as well as incorporating other wirelesscommunication technologies, such as wireless fidelity (Wi-Fi), intotheir service infrastructure. One result of reducing cell sizes andincorporating other wireless communication technologies is that therelationship between Wi-Fi (or other technologies) installations andcellular infrastructure is becoming closer than ever.

Historically, Wi-Fi and many other non-3GPP communication technologieshad a “grassroots” upbringing where access was typically provided byindividual establishments. Over time, business aggregators began toappear that offered users access to large numbers of individually ownedand managed Wi-Fi hotspots using a single accounting and authenticationplatform. Some market actors even began systematic deployments of Wi-Fihotspots at strategic locations such as airports, hotels, and chainrestaurants.

Concurrently, cellular (e.g., 3GPP) providers also began to add Wi-Fihotspot service to their access product offer list, complementary totraditional cellular services, either by owning their own Wi-Fioperations or forming a business alliance with a hotspot serviceprovider. Accordingly, Wi-Fi and other non-3GPP access networks werehistorically operated as separate networks with no direct connection to3GPP (or other) cellular networks other than the fact all mightinterface to the global Internet.

Recently, there has been a push to technologically integratenon-cellular access platforms into cellular access platforms. Forexample, with advances in cellular standards and technologies, cellular(e.g., LTE) providers are incorporating non-cellular (e.g., Wi-Fi)service into associated service infrastructure in a more integratedmanner. For instance, different than before, cellular networks might useboth LTE and Wi-Fi access links flexibly. In addition, the transition ofdata traffic from one access network to another, as well as splittingand merging of data traffic over these access networks links might beaccomplished seamlessly. Thus, user traffic can be transparently carriedby either or both LTE and Wi-Fi accesses, without affecting upper layerapplications and services.

For example, 3GPP standards define how non-3GPP access can be integratedinto LTE cellular infrastructure in specification TS 23.402, which isincorporated herein by reference. A number of architectural designs arespecified for different application situations such as roaming vs.non-roaming, local breakout vs. home-routed, etc. However, all suchdocuments share the same fundamental approach. Essentially, a mobiledevice or other UE attached to a non-3GPP access network is required toform a “tunnel” to a packet data network gateway (PGW) in the evolvedpacket core of the LTE cellular infrastructure over the non-3GPP linkand the associated access network. Outgoing IP traffic from the UE istunneled from the UE via the non-3GPP access to the PGW then forwardedto the external IP network, e.g. the Internet. Incoming IP traffic thatarrives at the PGW can be forwarded to the UE via this tunnel.Accordingly, the PGW operates as the traffic anchor point for the UEboth for supporting mobility and change of access technologies.

While the above approach maintains a unified solution for incorporatingdifferent kinds of non-3GPP access technologies, including Wi-Fi, WiMAX,and other types of wireless IP access technologies, the design of usingthe PGW as an anchor point also implies that to the 3GPP cellularnetwork, these non-3GPP accesses are both external in the sense thatbackhauls to these accesses are not owned and controlled by the cellularoperators, and remote in terms of network topology.

Moreover, as noted previously, there is a movement in the industrytoward smaller cells as opposed to large wireless towers. For example,small cell base station hardware is often capable of also providingWi-Fi access. Moreover, small cell base stations are often themselvesbecoming “external” because such cells can be deployed on externalnetworks such as customer enterprise Ethernets, which are both not undercellular operator control and often shared with customer Wi-Fi accesspoints covering the same physical areas.

Based on these observations, the solution to integrating non-cellularcommunication with cellular communication as proposed by TS 23.402 andother related documents can be improved. For example, the disclosedsubject matter can leverage the fact that in many cases an evolved nodeB(eNodeB) of an LTE cellular network can be co-located with anon-cellular (e.g., Wi-Fi) access point device. Due to such co-location,it is no longer necessary or advantageous to use the PGW as an anchorpoint or forming tunnels between the UE and the PGW, as is detailed byTS 23.402. Rather, some embodiments of the disclosed subject matter canestablish tunnels over non-3GPP accesses between the UE and the eNodeBserving that UE. Such can allow for tightly coupled 3GPP and non-3GPPaccess installations. Such an approach can provide for numerousadvantages such as, e.g., reduced signaling overhead, simplifiedquality-of-service management, and a more rapid reaction to changes ofaccess. Such advantages can arise due to the fact that tunnels can bemanaged locally between the UE and the serving eNodeB, rather than beingmanaged in the core network by a gateway such as the PGW.

In some embodiments, the disclosed subject matter can provide anenhancement to the current 3GPP architecture for incorporating non-3GPPaccesses. The disclosed subject matter can be fully compatible andcomplementary to the above mentioned 3GPP designs for incorporatingnon-3GPP accesses. In particular, embodiments of the disclosed subjectmatter provide for seamless integration of different non-3GPP accesstechnologies onto a 3GPP cellular platform for situations where thenon-3GPP accesses are provided in a manner that are networkedtopologically closer to 3GPP access than what the 3GPP designs forcurrently. Embodiments of the disclosed subject matter can takeadvantage of such “closeness” and can offer a more efficient way ofsupporting tight integration of non-3GPP accesses to 3GPPinfrastructure.

The disclosed subject matter is now described with reference to thedrawings, wherein like reference numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the disclosed subject matter. It may beevident, however, that the disclosed subject matter may be practicedwithout these specific details. In other instances, well-knownstructures and devices are shown in block diagram form in order tofacilitate describing the disclosed subject matter.

Long term evolution (LTE) is a standard for cellular-based wirelesscommunication maintained by the third generation partnership project(3GPP). Although the subject matter disclosed herein relates to suchstandards, it is appreciated that the terms “LTE” and “3GPP,” as usedherein, can relate to substantially any cellular-based wirelesscommunication network. That is, in some embodiments, the terms “LTE,”“3GPP,” and “cellular” can be used interchangeably. The terms “non-LTE,”“non-3GPP,” and “non-cellular” can also be used interchangeably hereinand are intended to denote communication standards, protocols, ortechnologies, typically wireless (e.g., wireless fidelity (Wi-Fi),worldwide interoperability for microwave access (WiMAX), high ratepacket data (HRPD), etc.), which differ from cellular-based standards,protocols, or technologies such as 3GPP or LTE.

Referring now to the drawing, with reference initially to FIG. 1, mobiledevice 100 is depicted. Mobile device 100 can provide for non-cellularlink integration with cellular networks. Mobile device 100 can representany suitable user equipment (UE) that can access data or services of acellular network provider, and can include a memory to storeinstructions and, coupled to the memory, a processor that facilitatesexecution of the instructions to perform operations. Examples of thememory and processor can be found with reference to FIG. 14. It is to beappreciated that the computer 1402 can represent a service device of acommunications network or a user equipment device and can be used inconnection with implementing one or more of the systems or componentsshown and described in connection with FIG. 1 and other figuresdisclosed herein.

In particular, mobile device 100 can be configured to establish firstcommunication path 102 with access point device 104. Access point device104 can be a wireless-type access point device, e.g., a Wi-Fi device, aWiMax device, a HRPD-based device, or substantially any other accesspoint device that operates according to protocol 106 that isnon-cellular in nature. For example, protocol 106 can be a protocol thatdiffers from a cellular protocol such as a 3GPP protocol or LTE protocol112. First communication path 102 can relate to a communications linkestablished between mobile device 100 and access point device 104.

Mobile device 100 can be configured to determine that access pointdevice 104 is co-located with eNodeB device 108, which can beaccomplished by way of co-location determination 110. The eNodeB device108 can be configured to operate according to LTE protocol 112 inconnection with communication with network device 114 of communicationnetwork 116. It is understood that communication network 116 can be anLTE network and can include LTE-enabled devices or paths, such as eNodeBdevice 108, mobile device 100, and second communication path 118. Insome embodiments, network device 114 can be a gateway device (e.g., aPGW device) that resides in a core network portion of communicationnetwork 116, which can be a cellular-based communication network, suchas 3GPP or LTE.

Co-location determination 110 can relate to a data discovery techniqueor any other suitable technique by which it can be determined thataccess point device 104 and eNodeB device 108 are co-located. Forexample, co-location determination 110 can relate to determining thataccess point device 104 and eNodeB device 108 are physically co-locatedand/or comprise a common physical structure. The common physicallystructure will typically be a common housing, casing, or enclosure, butcan also relate to a common tower or antenna array. Such embodiments arereferred to herein as “embedded co-location,” and described in moredetail in with reference to FIG. 3.

In some embodiments, co-location determination 110 can relate todetermining that access point device 104 and eNodeB device 108 aretopologically co-located with respect to a defined network topology. Forexample, the access point device 104 and the eNodeB device can representtopologically close nodes (or share a common node) on a shared Ethernetor other local area network (LAN). Such embodiments are referred toherein as “tunneled co-location,” and described in more detail inconnection with reference to FIG. 4. In the case of tunneledco-location, mobile device 100 can further provide for receiving anindication (or otherwise determining) that a secure tunnel has beenestablished between the access point device 104 and the eNodeB device108 (that are topologically close to one another). The secure tunnel canbe a secure communication path between access point device 104 andeNodeB device 108.

Mobile device 100 can be further configured to establish secondcommunication path 118 with eNodeB device 108. Second communication path118 can be established in connection with LTE protocol 112 (or anothersuitable cellular-based protocol). It is understood that the terms“first” and “second” are not intended in this case to imply a temporalorder. For example, second communication path 118 can exist prior toestablishing first communication path 102. Mobile device 100 can befurther configured to communicate data 120 and/or 122 between mobiledevice 100 and network device 114 via path 130 (e.g., 130 a-130 c) thattraverses first communication path 102 and eNodeB device 108. Forexample, mobile device 100 can transmit outgoing data (e.g., uplink data120) to network device 114 via path 130 or receive incoming data (e.g.,downlink data 122) from network device 114 via path 130.

It is appreciated that such differs from other solutions that form atunnel between the UE and the PGW. Such tunnels made by other solutionscompletely by-pass the associated eNodeB and therefore do not leveragethe advantages that can be obtained due to the fact that the eNodeBdevice and the non-cellular access point (e.g., Wi-Fi) device arephysically and/or network topologically close.

Various aspects of the disclosed subject matter can be facilitated bycontroller components or modules. In some embodiments, mobile device 100can comprise the controller component (e.g., UE controller 150). In someembodiments, eNodeB device 108 can comprise the controller component(e.g., eNodeB controller 160). In some embodiments, mobile device 100and eNodeB device 108 can each comprise a respective controller 150,160. These controller components (e.g., UE controller 150 and eNodeBcontroller 160) can manage or facilitate the operations detailed hereinas well as determine how communications are to be transported in amanner that provides additional efficiencies and other advantages whilestill remaining compliant with other solutions, which is furtherdetailed herein, particularly with respect to FIGS. 6-8B.

Turning now to FIG. 2, example integrated network 200 is provided.Integrated network 200 is intended to represent a cellular network(e.g., a long term evolution network) that facilitates integration witha non-cellular network. The various network devices associated with theLTE or cellular network are depicted at the upper portion while thevarious devices associated with the non-LTE network (e.g., Wi-Fi) aredepicted at the lower portion. The radio access network (RAN) portion ofboth networks are depicted on the left portion, while the core network(CN) portions of both networks are depicted on the right portion of FIG.2. The RAN portion generally provides radio wireless access for mobileunits (e.g., UE) via base stations. The RAN portion generally comprisesmobile units, base stations, and any additional components forcoordinating radio related operations. The CN portion generallycomprises various gateways for interfacing with both RAN and externalnetworks (e.g. the Internet), and components or devices for functionssuch as authentication, admission control, and charging.

As noted previously, other solutions associated with integratingnon-cellular links with cellular networks are directed to utilizing thepacket data network gateway, or PGW, which exists in the core network,as the anchor point, as illustrated by reference numeral 202. Forexample, other solutions for non-LTE access to the LTE communicationnetwork relies on the operation of forming a tunnel for non-LTE accessto the PGW. This PGW serves both as the anchor point for supportingnon-LTE access as well as user traffic mobility across LTE and non-LTEaccesses.

In contrast to other solutions, embodiments of the disclosed subjectmatter can provide certain advantages, particularly in connection withdeployment scenarios where the non-cellular (e.g., non-LTE or non-3GPP)access (via e.g., a Wi-Fi access point) and the cellular access (viae.g., an eNodeB) are co-located. For example, co-location can occur incases where the non-cellular access is provided by an interface that ison the platform of the eNodeB, or at a location that is topologicallyclose to the eNodeB, e.g., on the same Ethernet that the eNodeB isconnected to. Such non-cellular access can be referred to as “co-locatednon-cellular access.” It is to be understood that co-location is not arequirement of the disclosed subject matter, but such deploymentscenarios are believed to optimize the advantages of the disclosedsubject matter, while reducing security concerns.

Referring now to FIG. 3, system 300 is depicted. System 300 relates toan embedded co-location embodiment of the disclosed subject matter. Theembedded co-location embodiment can be characterized by eNodeB device108 and access point device 104 sharing common structure or housing 302.The UE (in this case mobile device 100), can establish multiple linkswith eNodeB device 108. Such can include one or more LTE protocol-basedpaths (e.g., LTE-Uu) as well as one or more non-LTE connections withaccess point device 104 that can also connect to eNodeB device 108 viaaccess point device 104 that is on the same platform. Thus,communication via access point device 104 can be integrated with the LTEplatform at eNodeB device 108 (e.g., in the RAN portion of communicationnetwork 116) rather than at the PGW (e.g., in the core network portionof communication network 116).

With reference now to FIG. 4, system 400 is depicted. System 400 relatesto a tunneled co-location embodiment of the disclosed subject matter.The tunneled co-location embodiment can be characterized by eNodeBdevice 108 and access point device 104 sharing common local area network(LAN) 402 such as an Ethernet. The UE (in this case mobile device 100),can again establish multiple links with eNodeB device 108. Such caninclude one or more LTE protocol-based paths (e.g., LTE-Uu) as well asone or more non-LTE connections with access point device 104. Securetunnel(s) 404 can be established between eNodeB device 108 and accesspoint device 104. Secure tunnel(s) 404 can be secure communicationpath(s) between access point device 104 and eNodeB device 108 and canrepresent non-LTE access to eNodeB device 108. Hence, in any exemplaryscenario, either embedded co-location, tunneled co-location, or anothersuitable embodiment, communication via access point device 104 can beintegrated with the LTE platform at eNodeB device 108 rather than at thepacket data network gateway.

Turning now to FIGS. 5A-5C, diagrams 500, 520, and 530 are presented.Diagram 500 illustrates various example LTE bearers. Existing LTEstandards provide for various communication paths between variousdevices of the LTE network, which are referred to as bearers. Generally,bearers are virtual end-to-end “pipes” that are created within thecellular network between different components. For example, radio bearer502 can accommodate traffic between the UE and the eNodeB. S1 bearer 504can accommodate traffic between the eNodeB and the serving gateway (SGW)of a core network portion of the LTE network. S5/S8 bearer 506 canaccommodate traffic between the SGW and the PGW. Evolved radio accessbearer (E-RAB) 508 can accommodate traffic between the UE and the SGW.Evolved packet system (EPS) bearer 510 can accommodate traffic betweenthe UE and the PGW.

Diagram 520 illustrates an example set of links between mobile device100 and access point device 104. The set of links can include links 522₁-522 _(N), where N can be virtually any positive integer. Links 522₁-522 _(N) can be referred to herein, either individually orcollectively as link(s) 522. All or a portion of links 522 mightpre-exist or might be established based on instructions from one or morecontroller 150 or 160. It is appreciated that first communication path102 can be a member of the set of links 522.

Diagram 530 illustrates an example set of virtual tunnels between mobiledevice 100 and eNodeB device 108. These virtual tunnels 532-540, as wellas others not shown, can relate to secure communication paths betweenmobile device 100 and eNodeB device 108. In some embodiments, virtualtunnels 532-540 can comprise various links 522. In other words, virtualtunnels 532-540 can traverse access point device 104, although in otherembodiments, such is not the case.

In some embodiments, virtual tunnels 532-540, as well as others notshown, can correspond to respective bearers 502-510, depicted inillustration 500 of FIG. 5, as well as others not shown. To illustrate,virtual companion tunnel 532 can correspond to radio bearer 502. Virtualtunnel 534 can correspond to S1 bearer 504. Likewise, tunnel 536 cancorrespond to S5/S8 bearer 506; tunnel 538 can correspond to E-RAB 508;and tunnel 540 can correspond to EPS bearer 510. Additional detail inconnection with bearers 502-510, links 522 and virtual tunnels 532-540is further detailed herein.

For example, while still referring to FIGS. 5A-5C, but turning back toFIG. 1, it can be appreciated that the disclosed subject matter can beimplemented systems that also implement other solutions such as thoseproposed by TS 23.402. For instance, embodiments of the disclosedsubject matter can be implemented for deployment scenarios where thenon-LTE access point device and the eNodeB device are co-located, withother solutions implemented for other deployment scenarios. Regardless,one of the advantages of embodiments of the disclosed subject matter isthat interfaces between the eNodeB and the CN portion of thecommunication network can remain unaltered. Put another way,compatibility with 3GPP specifications, both in the CN and in the RANcan be maintained. Such compatibility can be accomplished by controllers150 and/or 160. For example, controllers 150, 160 can interface with the3GPP means of transporting user plane packets in its CN, namely thebearers detailed in connection with FIG. 5A, which illustrates the bearsspecified by 3GPP LTE standards.

In some embodiments of the disclosed subject matter, the controllers150, 160 can interact with the session management procedures of the 3GPPbearers (e.g., bearers 502-510). For example, because of the inclusionand exclusion of additional access links (e.g., links 522) from time totime, the controller 150, 160 can update the bearer state to reflect theuse of these non-3GPP links 522 (which can include first communicationpath 102). For user plane communications between mobile device 100 andeNodeB device 108, essentially packets of the data (e.g., uplink data120 or downlink data 122) can be extracted from the 3GPP bearers (e.g.,bearers 502-510) at one end (e.g., at eNodeB device 108), placed ontonon-3GPP links 522, then re-insert them back onto the originalassociated 3GPP bearers at the other end (e.g., at mobile device 100).Because there may exist multiples of each type of bearer 502-510 anassociated multiple number of non-3GPP links 522 can be established andcontrollers 150, 160 can perform a mapping function for identifyingwhich bearer to insert packets of data 120, 122 upon arrival from anon-3GPP link 522, and which non-3GPP link 522 to employ to transportpackets of data 120, 122 as such packets are extracted from a bearer502-510.

In some embodiments, mobile device 100 and/or eNodeB device 108 canutilize an associated controller 150, 160 to identify a set of bearers502-510 and a set of links 522. As described, the set of bearers 502-510can relate to communication paths fashioned in accordance with LTEprotocol 112 between a first device of communication network 116 and asecond device of communication network 116. The set of links 522 canrelate communication paths, including first communication path 102,fashioned in accordance with non-LTE protocol 106 that differs from LTEprotocol 112 between mobile device 100 and access point device 104, andpotentially extending to eNodeB device 108 via path(s) 130 b. Additionaldetail can be found at FIG. 6, which can now be referenced.

FIG. 6 illustrates system 600. System 600 can provide for additionalaspects, features, or detail in connection with integrating non-LTElinks with an LTE network. In some embodiments, system 600 can relate tomobile device 100 that, along with UE controller 150, can performoperations denoted by reference numerals 602-614. In some embodiments,all or a portion of operations 602-614 can be performed by eNodeB device108 and associated eNodeB controller 160.

For example, device 100 or device 108 (and/or controller 150, 160) candetermine a bearer (e.g., EPS bearer 510) from a set of bearers 502-510associated with data 120, 122, which is detailed in connection withreference numeral 602. Next, at reference numeral 604, a link 522 fromthe set of links 522 can be selected for transporting data 120, 122 thatother solutions expect to be transported on the EPS bearer 510. Theselected link 522 can be denoted as first communication path 102.

As previously noted, controllers 150, 160 can process a mapping functionto map bearers to links 522. To facilitate such mapping, in oneembodiment, the controller 150, 160 on the egress entity (e.g., device100 or device 108 with outgoing data 120, 122) of the 3GPP bearer tagspackets of outgoing data 120, 122 exiting the 3GPP bearer onto non-3GPPlinks 522 with additional information so that the controller 150, 160 onthe ingress entity (e.g., device 100 or device 108 with incoming data120, 122) of the 3GPP bearers is able to map the packet of data 120, 122back to a particular established 3GPP bearer. Tagging data 120, 122 withtag information of a particular bearer is depicted at reference numeral606.

Hence, as a packet of data 120, 122 arrives over a 3GPP bearer,controller 150, 160 can identify the bearer, and then generates theextra information needed for tagging the data 120, 122 for the purposeof bearer identification. The controller 150, 160 can also identify overwhich non-3GPP link 522 the packet of data 120, 122 is to be sent basedon the conditions of the link 522 at the time and an associated linkselection algorithm. This link selection process may also depend oncharacteristics of the packets themselves, such as which applicationflows they belong to or what quality-of-service characteristics orsecurity requirements are defined. Data 120, 122 can be sent over theselected link 522 with tagged information. In some embodiments, data120, 122 with tagged information can be sent from the egress entity viamultiple links 522, which is illustrated by reference numeral 608.

At the other end, that is, for the ingress entity (e.g., device 100 ordevice 108), the controller 150, 160 can identify the 3GPP bearer that apacket belongs to as it arrives over a non-3GPP link 522 by using thetagged information, which is detailed in connection with referencenumeral 610. In embodiments where virtual companion tunnels 532-540 areutilized, the 3GPP bearer can be identified based on the non-3GPPvirtual tunnel 532-540 by which data 120, 122 arrives at the ingressentity. Regardless of how the bearer is identified, data 120, 122 can beinserted into a queue for the identified bearer by the ingress entity,described at 612. In some embodiments, data 120, 122 can be reformattedaccording to a bearer protocol of the identified bearer prior toinserting into the identified bearer, as described at 614. It isunderstood that controllers 150, 160 and/or devices 100, 108 can enforcequality-of-service settings (e.g., max/min bit rates) of the 3GPPbearers when inserting data 120, 122 back to these bearers. Additionallyor alternatively, controllers 150, 160 can alter quality-of-servicesettings of the bearer through the 3GPP standard session managementprocedures.

Referring now to FIGS. 7A and 7B, illustrations 700 and 710 aredepicted. Illustration 700 provides for an embedded co-locationembodiment in which non-3GPP link layer frames carry data 120, 122.Illustration 710 provides for an embedded co-location embodiment inwhich data 120, 122 is encapsulated by another layer of IP header, e.g.,IP-in-IP encapsulation. FIG. 3 provides an example of embeddedco-location embodiments.

For example, for uplink data 120 traffic (e.g., traffic from mobiledevice 100 to access point device 104 and/or eNodeB 108), UE controller150 can determine for any given packet of data 120 which path to take,either via the interface for existing 3GPP paths (e.g., secondcommunication paths 118, bearers 502-510, etc.), or the non-3GPPinterface for existing or newly created links 522. It is appreciatedthat, in some embodiments, the former implementation described byillustration 700 can be more efficient, but might require closerinteractions with the IP layer implementation of the host, if it isassumed there is no modification of existing IP layers to deal withmultiple outgoing interfaces. In some embodiments, the latterimplementation described by illustration 710 might incur additionaloverhead relative to the former implementation, such as in outer layerIP headers. However, the latter implementation can, in some embodiments,be more flexible in terms of implementation because such can depend lesson accesses to the internals of the lower layers of the communicationprotocol stack, and can be more seamlessly integrated with no change toIP layer implementations.

Referring now to FIGS. 8A and 8B, illustrations 800 and 810 aredepicted. Illustration 800 provides for a tunneled co-locationembodiment in which a non-3GPP bridging access point resides on a sameLAN as the eNodeB device 108. Illustration 810 provides for tunneledco-location embodiment in which the non-3GPP bridging access pointresides on a higher IP layer as part of a routing function. FIG. 4provides an example of tunneled co-location embodiments.

For instance, illustrations 800 and 810 depict the protocol stack fordifferent entities for the tunneled co-location cases. In such cases, aseparate entity provides the non-3GPP access services to the UE (e.g.,mobile device 100). This entity is referred to as the non 3GPP bridgingaccess point. As introduced above, a difference between illustration 800and 810 relates to the function in the non-3GPP bridging access pointthat performs the forwarding. In the first case of illustration 800, thenon-3GPP bridging access point is on the same LAN as the eNodeB (e.g.,eNodeB device 108) and the packet forwarding is performed at thebridging layer. In the second case of illustration 810, suchfunctionality is performed by devices residing above the IP layer aspart of the routing function.

FIGS. 9-11 illustrate various methodologies in accordance with thedisclosed subject matter. While, for purposes of simplicity ofexplanation, the methodologies are shown and described as a series ofacts, it is to be understood and appreciated that the disclosed subjectmatter is not limited by the order of acts, as some acts may occur indifferent orders and/or concurrently with other acts from that shown anddescribed herein. For example, those skilled in the art will understandand appreciate that a methodology could alternatively be represented asa series of interrelated states or events, such as in a state diagram.Moreover, not all illustrated acts may be required to implement amethodology in accordance with the disclosed subject matter.Additionally, it should be further appreciated that the methodologiesdisclosed hereinafter and throughout this specification are capable ofbeing stored on an article of manufacture to facilitate transporting andtransferring such methodologies to computers.

Turning now to FIG. 9, exemplary method 900 is depicted. Method 900 canprovide for integrating non-LTE links with LTE networks. Generally, atreference numeral 902, a first indication can be received. The firstindication can indicate that a first communication path has beenestablished between an access point device that operates according to aprotocol that differs from a long term evolution protocol and a userequipment device that supports the protocol and the long term evolutionprotocol.

At reference numeral 904, a second indication can be received. Thesecond indication can indicate that a second communication path has beenestablished between the user equipment and an eNodeB device according tothe long term evolution protocol.

At reference numeral 906, it can be determined that the access pointdevice and the eNodeB device are co-located and connected by a thirdcommunication path. Method 900 can proceed via insert A described inFIG. 10, or continue to reference numeral 908. At reference numeral 908,communication of data can be facilitated between the user equipment anda network device in a core network portion of a communication networkvia the third communication path. The communication network can operateaccording to the long term evolution protocol.

Turning now to FIG. 10, exemplary method 1000 is illustrated. Method1000 can provide for various example techniques associated withdetermining that the access point device and the eNodeB device areco-located. For example, method 1000 can initially proceed to referencenumeral 1002. At reference numeral 1002, the determining that the accesspoint device and the eNodeB device are co-located as detailed inconnection with reference numeral 906 of FIG. 9 can comprise determiningthat the access point device and the eNodeB device are physicallyco-located and comprise a common physical structure (e.g., in the samebox or housing or the same tower). Method 1000 can thereafter end andreturn to reference numeral 906 of FIG. 9.

Additionally or alternatively, method 1000 can initially proceed toreference numeral 1004. At reference numeral 1004, the determining thatthe access point device and the eNodeB device are co-located as detailedin connection with reference numeral 906 of FIG. 9 can comprisedetermining that the access point device and the eNodeB device aretopologically co-located with respect to a defined network topology(e.g., on the same node or proximal nodes of a common LAN).

At reference numeral 1006, an indication can be received. The indicationcan indicated that a secure tunnel has been established between theaccess point device and the eNodeB device. The secure tunnel can be asecure communication path between the access point device and the eNodeBdevice. Thereafter, method 1000 can end and return to reference numeral906 of FIG. 9.

Referring now to FIG. 11, exemplary method 1100 is illustrated. Method1100 can provide for additional features or aspects in connection withintegrating non-LTE links with LTE networks. Method 1100 can initiallyproceed to reference numeral 1102 or 1112, e.g., depending on thecommunication path by which data is received and/or whether data isreceived by an ingress device or an egress device and/or whether thedata is associated with an LTE protocol or a protocol that differs fromLTE.

For example, at reference numeral 1102, data can be received via a longterm evolution protocol bearer. In that case, method 1100 can proceed toreference numerals 1104-1110 and thereafter terminate. At referencenumeral 1112, data can be received via a link that operates according toa different protocol that differs from the long term evolution protocolor, in some embodiments, via a virtual companion tunnel that operatesaccording to the different protocol. In the second case, method 1100 canproceed to reference numeral 1114-1118, and thereafter end.

At reference numeral 1104, the bearer can be identified. For example,the bearer by which data was received in connection with referencenumeral 1102. At reference numeral 1106, the data can be tagged with taginformation associated with the bearer and/or an identity of the beareridentified in connection with reference numeral 1104. At referencenumeral 1108, an appropriate non-LTE link or non-LTE virtual companiontunnel can be identified and selected for sending the data received atreference numeral 1102 and tagged at reference numeral 1106. Atreference numeral 1110, the data can be transmitted via the selectedlink and/or tunnel.

At reference numeral 1114, the bearer that originally carried the datareceived at 1102 (e.g., by an egress device), can be identified (e.g.,by an ingress device that receives the tagged data transmitted atreference numeral 1110). In particular, the bearer can be identifiedbased on the tag information or based on the virtual companion tunnel bywhich the tagged data arrives. At reference numeral 1116, the data canbe reformatted according to the bearer protocol. In some embodiments,reformatting the data might not be necessary to remain compliant withthe bearer protocol. At reference numeral 1118, the data can be insertedinto a queue associated with the bearer.

To provide further context for various aspects of the subjectspecification, FIG. 12 illustrates an example wireless communicationenvironment 1200, with associated components that can enable operationof a femtocell enterprise network in accordance with aspects describedherein. Wireless communication environment 1200 includes two wirelessnetwork platforms: (i) A macro network platform 1210 that serves, orfacilitates communication) with user equipment 1275 via a macro radioaccess network (RAN) 1270. It should be appreciated that in cellularwireless technologies (e.g., 4G, 3GPP UMTS, HSPA, 3GPP LTE, 3GPP UMB),macro network platform 1210 is embodied in a Core Network. (ii) A femtonetwork platform 1280, which can provide communication with UE 1275through a femto RAN 1290, linked to the femto network platform 1280through a routing platform 122 via backhaul pipe(s) 1285. It should beappreciated that femto network platform 1280 typically offloads UE 1275from macro network, once UE 1275 attaches (e.g., through macro-to-femtohandover, or via a scan of channel resources in idle mode) to femto RAN.

It is noted that RAN includes base station(s), or access point(s), andits associated electronic circuitry and deployment site(s), in additionto a wireless radio link operated in accordance with the basestation(s). Accordingly, macro RAN 1270 can comprise various coveragecells like cell 1205, while femto RAN 1290 can comprise multiple femtoaccess points. As mentioned above, it is to be appreciated thatdeployment density in femto RAN 1290 is substantially higher than inmacro RAN 1270.

Generally, both macro and femto network platforms 1210 and 1280 includecomponents, e.g., nodes, gateways, interfaces, servers, or platforms,that facilitate both packet-switched (PS) (e.g., internet protocol (IP),frame relay, asynchronous transfer mode (ATM)) and circuit-switched (CS)traffic (e.g., voice and data) and control generation for networkedwireless communication. In an aspect of the subject innovation, macronetwork platform 1210 includes CS gateway node(s) 1212 which caninterface CS traffic received from legacy networks like telephonynetwork(s) 1240 (e.g., public switched telephone network (PSTN), orpublic land mobile network (PLMN)) or a SS7 network 1260. Circuitswitched gateway 1212 can authorize and authenticate traffic (e.g.,voice) arising from such networks. Additionally, CS gateway 1212 canaccess mobility, or roaming, data generated through SS7 network 1260;for instance, mobility data stored in a VLR, which can reside in memory1230. Moreover, CS gateway node(s) 1212 interfaces CS-based traffic andsignaling and gateway node(s) 1218. As an example, in a 3GPP UMTSnetwork, gateway node(s) 1218 can be embodied in gateway GPRS supportnode(s) (GGSN).

In addition to receiving and processing CS-switched traffic andsignaling, gateway node(s) 1218 can authorize and authenticate PS-baseddata sessions with served (e.g., through macro RAN) wireless devices.Data sessions can include traffic exchange with networks external to themacro network platform 1210, like wide area network(s) (WANs) 1250; itshould be appreciated that local area network(s) (LANs) can also beinterfaced with macro network platform 1210 through gateway node(s)1218. Gateway node(s) 1218 generates packet data contexts when a datasession is established. To that end, in an aspect, gateway node(s) 1218can include a tunnel interface (e.g., tunnel termination gateway (TTG)in 3GPP UMTS network(s); not shown) which can facilitate packetizedcommunication with disparate wireless network(s), such as Wi-Finetworks. It should be further appreciated that the packetizedcommunication can include multiple flows that can be generated throughserver(s) 1214. It is to be noted that in 3GPP UMTS network(s), gatewaynode(s) 1218 (e.g., GGSN) and tunnel interface (e.g., TTG) comprise apacket data gateway (PDG).

Macro network platform 1210 also includes serving node(s) 1216 thatconvey the various packetized flows of information or data streams,received through gateway node(s) 1218. As an example, in a 3GPP UMTSnetwork, serving node(s) can be embodied in serving GPRS support node(s)(SGSN).

As indicated above, server(s) 1214 in macro network platform 1210 canexecute numerous applications (e.g., location services, online gaming,wireless banking, wireless device management . . . ) that generatemultiple disparate packetized data streams or flows, and manage (e.g.,schedule, queue, format . . . ) such flows. Such application(s), forexample can include add-on features to standard services provided bymacro network platform 1210. Data streams can be conveyed to gatewaynode(s) 1218 for authorization/authentication and initiation of a datasession, and to serving node(s) 1216 for communication thereafter.Server(s) 1214 can also effect security (e.g., implement one or morefirewalls) of macro network platform 1210 to ensure network's operationand data integrity in addition to authorization and authenticationprocedures that CS gateway node(s) 1212 and gateway node(s) 1218 canenact. Moreover, server(s) 1214 can provision services from externalnetwork(s), e.g., WAN 1250, or Global Positioning System (GPS)network(s) (not shown). It is to be noted that server(s) 1214 caninclude one or more processor configured to confer at least in part thefunctionality of macro network platform 1210. To that end, the one ormore processor can execute code instructions stored in memory 1230, forexample.

In example wireless environment 1200, memory 1230 stores informationrelated to operation of macro network platform 1210. Information caninclude business data associated with subscribers; market plans andstrategies, e.g., promotional campaigns, business partnerships;operational data for mobile devices served through macro networkplatform; service and privacy policies; end-user service logs for lawenforcement; and so forth. Memory 1230 can also store information fromat least one of telephony network(s) 1240, WAN(s) 1250, or SS7 network1260, enterprise NW(s) 1265, or service NW(s) 1267.

Femto gateway node(s) 1284 have substantially the same functionality asPS gateway node(s) 1218. Additionally, femto gateway node(s) 1284 canalso include substantially all functionality of serving node(s) 1216. Inan aspect, femto gateway node(s) 1284 facilitates handover resolution,e.g., assessment and execution. Further, control node(s) 1220 canreceive handover requests and relay them to a handover component (notshown) via gateway node(s) 1284. According to an aspect, control node(s)1220 can support RNC capabilities.

Server(s) 1282 have substantially the same functionality as described inconnection with server(s) 1214. In an aspect, server(s) 1282 can executemultiple application(s) that provide service (e.g., voice and data) towireless devices served through femto RAN 1290. Server(s) 1282 can alsoprovide security features to femto network platform. In addition,server(s) 1282 can manage (e.g., schedule, queue, format . . . )substantially all packetized flows (e.g., IP-based, frame relay-based,ATM-based) it generates in addition to data received from macro networkplatform 1210. It is to be noted that server(s) 1282 can include one ormore processor configured to confer at least in part the functionalityof macro network platform 1210. To that end, the one or more processorcan execute code instructions stored in memory 1286, for example.

Memory 1286 can include information relevant to operation of the variouscomponents of femto network platform 1280. For example operationalinformation that can be stored in memory 1286 can comprise, but is notlimited to, subscriber information; contracted services; maintenance andservice records; femto cell configuration (e.g., devices served throughfemto RAN 1290; access control lists, or white lists); service policiesand specifications; privacy policies; add-on features; and so forth.

It is noted that femto network platform 1280 and macro network platform1210 can be functionally connected through one or more reference link(s)or reference interface(s). In addition, femto network platform 1280 canbe functionally coupled directly (not illustrated) to one or more ofexternal network(s) 1240, 1250, 1260, 1265 or 1267. Reference link(s) orinterface(s) can functionally link at least one of gateway node(s) 1284or server(s) 1286 to the one or more external networks 1240, 1250, 1260,1265 or 1267.

FIG. 13 illustrates a wireless environment that includes macro cells andfemtocells for wireless coverage in accordance with aspects describedherein. In wireless environment 1305, two areas represent “macro” cellcoverage; each macro cell is served by a base station 1310. It can beappreciated that macro cell coverage area 1305 and base station 1310 caninclude functionality, as more fully described herein, for example, withregard to system 1300. Macro coverage is generally intended to servemobile wireless devices, like UE 1320 _(A), 1320 _(B), in outdoorslocations. An over-the-air (OTA) wireless link 1335 provides suchcoverage, the wireless link 1335 comprises a downlink (DL) and an uplink(UL), and utilizes a predetermined band, licensed or unlicensed, of theradio frequency (RF) spectrum. As an example, UE 1320 _(A), 1320 _(B)can be a 3GPP Universal Mobile Telecommunication System (UMTS) mobilephone. It is noted that a set of base stations, its associatedelectronics, circuitry or components, base stations controlcomponent(s), and wireless links operated in accordance to respectivebase stations in the set of base stations form a radio access network(RAN). In addition, base station 1310 communicates via backhaul link(s)1351 with a macro network platform 1360, which in cellular wirelesstechnologies (e.g., 3rd Generation Partnership Project (3GPP) UniversalMobile Telecommunication System (UMTS), Global System for MobileCommunication (GSM)) represents a core network.

In an aspect, macro network platform 1360 controls a set of basestations 1310 that serve either respective cells or a number of sectorswithin such cells. Base station 1310 comprises radio equipment 1314 foroperation in one or more radio technologies, and a set of antennas 1312(e.g., smart antennas, microwave antennas, satellite dish(es) . . . )that can serve one or more sectors within a macro cell 1305. It is notedthat a set of radio network control node(s), which can be a part ofmacro network platform 1360; a set of base stations (e.g., Node B 1310)that serve a set of macro cells 1305; electronics, circuitry orcomponents associated with the base stations in the set of basestations; a set of respective OTA wireless links (e.g., links 1315 or1316) operated in accordance to a radio technology through the basestations; and backhaul link(s) 1355 and 1351 form a macro radio accessnetwork (RAN). Macro network platform 1360 also communicates with otherbase stations (not shown) that serve other cells (not shown). Backhaullink(s) 1351 or 1353 can include a wired backbone link (e.g., opticalfiber backbone, twisted-pair line, T1/E1 phone line, a digitalsubscriber line (DSL) either synchronous or asynchronous, an asymmetricADSL, or a coaxial cable . . . ) or a wireless (e.g., line-of-sight(LOS) or non-LOS) backbone link. Backhaul pipe(s) 1355 link disparatebase stations 1310. According to an aspect, backhaul link 1353 canconnect multiple femto access points 1330 and/or controller components(CC) 1301 to the femto network platform 1302. In one example, multiplefemto APs can be connected to a routing platform (RP) 1387, which inturn can be connect to a controller component (CC) 1301. Typically, theinformation from UEs 1320 _(A) can be routed by the RP 1387, forexample, internally, to another UE 1320 _(A) connected to a disparatefemto AP connected to the RP 1387, or, externally, to the femto networkplatform 1302 via the CC 1301, as discussed in detail supra.

In wireless environment 1305, within one or more macro cell(s) 1305, aset of femtocells 1345 served by respective femto access points (APs)1330 can be deployed. It can be appreciated that, aspects of the subjectinnovation can be geared to femtocell deployments with substantive femtoAP density, e.g., 10⁴-10⁷ femto APs 1330 per base station 1310.According to an aspect, a set of femto access points 1330 ₁-1330 _(N),with N a natural number, can be functionally connected to a routingplatform 1387, which can be functionally coupled to a controllercomponent 1301. The controller component 1301 can be operationallylinked to the femto network platform 1302 by employing backhaul link(s)1353. Accordingly, UE 1320 _(A) connected to femto APs 1330 ₁-1330 _(N)can communicate internally within the femto enterprise via the routingplatform (RP) 1387 and/or can also communicate with the femto networkplatform 1302 via the RP 1387, controller component 1301 and thebackhaul link(s) 1353. It can be appreciated that although only onefemto enterprise is depicted in FIG. 13, multiple femto enterprisenetworks can be deployed within a macro cell 1305.

It is noted that while various aspects, features, or advantagesdescribed herein have been illustrated through femto access point(s) andassociated femto coverage, such aspects and features also can beexploited for home access point(s) (HAPs) that provide wireless coveragethrough substantially any, or any, disparate telecommunicationtechnologies, such as for example Wi-Fi (wireless fidelity) or picocelltelecommunication. Additionally, aspects, features, or advantages of thesubject innovation can be exploited in substantially any wirelesstelecommunication, or radio, technology; for example, Wi-Fi, WorldwideInteroperability for Microwave Access (WiMAX), Enhanced General PacketRadio Service (Enhanced GPRS), 3GPP LTE, 3GPP2 UMB, 3GPP UMTS, HSPA,HSDPA, HSUPA, or LTE Advanced. Moreover, substantially all aspects ofthe subject innovation can include legacy telecommunicationtechnologies.

With respect to FIG. 13, in example embodiment 1300, base station AP1310 can receive and transmit signal(s) (e.g., traffic and controlsignals) from and to wireless devices, access terminals, wireless portsand routers, etc., through a set of antennas 1312 ₁-1312 _(N). It shouldbe appreciated that while antennas 1312 ₁-1312 _(N) are a part ofcommunication platform 1325, which comprises electronic components andassociated circuitry that provides for processing and manipulating ofreceived signal(s) (e.g., a packet flow) and signal(s) (e.g., abroadcast control channel) to be transmitted. In an aspect,communication platform 1325 includes a transmitter/receiver (e.g., atransceiver) 1366 that can convert signal(s) from analog format todigital format upon reception, and from digital format to analog formatupon transmission. In addition, receiver/transmitter 1366 can divide asingle data stream into multiple, parallel data streams, or perform thereciprocal operation. Coupled to transceiver 1366 is amultiplexer/demultiplexer 1367 that facilitates manipulation of signalin time and frequency space. Electronic component 1367 can multiplexinformation (data/traffic and control/signaling) according to variousmultiplexing schemes such as time division multiplexing (TDM), frequencydivision multiplexing (FDM), orthogonal frequency division multiplexing(OFDM), code division multiplexing (CDM), space division multiplexing(SDM). In addition, mux/demux component 1367 can scramble and spreadinformation (e.g., codes) according to substantially any code known inthe art; e.g., Hadamard-Walsh codes, Baker codes, Kasami codes,polyphase codes, and so on. A modulator/demodulator 1368 is also a partof operational group 1325, and can modulate information according tomultiple modulation techniques, such as frequency modulation, amplitudemodulation (e.g., M-ary quadrature amplitude modulation (QAM), with M apositive integer), phase-shift keying (PSK), and the like.

Referring now to FIG. 14, there is illustrated a block diagram of anexemplary computer system operable to execute the disclosedarchitecture. In order to provide additional context for various aspectsof the disclosed subject matter, FIG. 14 and the following discussionare intended to provide a brief, general description of a suitablecomputing environment 1400 in which the various aspects of the disclosedsubject matter can be implemented. Additionally, while the disclosedsubject matter described above may be suitable for application in thegeneral context of computer-executable instructions that may run on oneor more computers, those skilled in the art will recognize that thedisclosed subject matter also can be implemented in combination withother program modules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the inventive methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the disclosed subject matter may also bepracticed in distributed computing environments where certain tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules can be located in both local and remote memory storage devices.

A computer typically includes a variety of computer-readable media.Computer-readable media can be any available media that can be accessedby the computer and includes both volatile and nonvolatile media,removable and non-removable media. By way of example, and notlimitation, computer-readable media can comprise computer storage mediaand communication media. Computer storage media can include eithervolatile or nonvolatile, removable and non-removable media implementedin any method or technology for storage of information such ascomputer-readable instructions, data structures, program modules orother data. Computer storage media includes, but is not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disk (DVD) or other optical disk storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other medium which can be used to store the desired informationand which can be accessed by the computer.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism, and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above should also be included within the scope ofcomputer-readable media.

Still referring to FIG. 14, the exemplary environment 1400 forimplementing various aspects of the disclosed subject matter includes acomputer 1402, the computer 1402 including a processing unit 1404, asystem memory 1406 and a system bus 1408. The system bus 1408 couples tosystem components including, but not limited to, the system memory 1406to the processing unit 1404. The processing unit 1404 can be any ofvarious commercially available processors. Dual microprocessors andother multi-processor architectures may also be employed as theprocessing unit 1404.

The system bus 1408 can be any of several types of bus structure thatmay further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1406includes read-only memory (ROM) 1410 and random access memory (RAM)1412. A basic input/output system (BIOS) is stored in a non-volatilememory 1410 such as ROM, EPROM, EEPROM, which BIOS contains the basicroutines that help to transfer information between elements within thecomputer 1402, such as during start-up. The RAM 1412 can also include ahigh-speed RAM such as static RAM for caching data.

The computer 1402 further includes an internal hard disk drive (HDD)1414 (e.g., EIDE, SATA), which internal hard disk drive 1414 may also beconfigured for external use in a suitable chassis (not shown), amagnetic floppy disk drive (FDD) 1416, (e.g., to read from or write to aremovable diskette 1418) and an optical disk drive 1420, (e.g., readinga CD-ROM disk 1422 or, to read from or write to other high capacityoptical media such as the DVD). The hard disk drive 1414, magnetic diskdrive 1416 and optical disk drive 1420 can be connected to the systembus 1408 by a hard disk drive interface 1424, a magnetic disk driveinterface 1426 and an optical drive interface 1428, respectively. Theinterface 1424 for external drive implementations includes at least oneor both of Universal Serial Bus (USB) and IEEE1394 interfacetechnologies. Other external drive connection technologies are withincontemplation of the subject matter disclosed herein.

The drives and their associated computer-readable media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1402, the drives and mediaaccommodate the storage of any data in a suitable digital format.Although the description of computer-readable media above refers to aHDD, a removable magnetic diskette, and a removable optical media suchas a CD or DVD, it should be appreciated by those skilled in the artthat other types of media which are readable by a computer, such as zipdrives, magnetic cassettes, flash memory cards, cartridges, and thelike, may also be used in the exemplary operating environment, andfurther, that any such media may contain computer-executableinstructions for performing the methods of the disclosed subject matter.

A number of program modules can be stored in the drives and RAM 1412,including an operating system 1430, one or more application programs1432, other program modules 1434 and program data 1436. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1412. It is appreciated that the disclosed subjectmatter can be implemented with various commercially available operatingsystems or combinations of operating systems.

A user can enter commands and information into the computer 1402 throughone or more wired/wireless input devices, e.g., a keyboard 1438 and apointing device, such as a mouse 1440. Other input devices (not shown)may include a microphone, an IR remote control, a joystick, a game pad,a stylus pen, touch screen, or the like. These and other input devicesare often connected to the processing unit 1404 through an input deviceinterface 1442 that is coupled to the system bus 1408, but can beconnected by other interfaces, such as a parallel port, an IEEE1394serial port, a game port, a USB port, an IR interface, etc.

A monitor 1444 or other type of display device is also connected to thesystem bus 1408 via an interface, such as a video adapter 1446. Inaddition to the monitor 1444, a computer typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1402 may operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1448. The remotecomputer(s) 1448 can be a workstation, a server computer, a router, apersonal computer, a mobile device, portable computer,microprocessor-based entertainment appliance, a peer device or othercommon network node, and typically includes many or all of the elementsdescribed relative to the computer 1402, although, for purposes ofbrevity, only a memory/storage device 1450 is illustrated. The logicalconnections depicted include wired/wireless connectivity to a local areanetwork (LAN) 1452 and/or larger networks, e.g., a wide area network(WAN) 1454. Such LAN and WAN networking environments are commonplace inoffices and companies, and facilitate enterprise-wide computer networks,such as intranets, all of which may connect to a global communicationsnetwork, e.g., the Internet.

When used in a LAN networking environment, the computer 1402 isconnected to the local network 1452 through a wired and/or wirelesscommunication network interface or adapter 1456. The adapter 1456 mayfacilitate wired or wireless communication to the LAN 1452, which mayalso include a wireless access point disposed thereon for communicatingwith the wireless adapter 1456.

When used in a WAN networking environment, the computer 1402 can includea modem 1458, or is connected to a communications server on the WAN1454, or has other means for establishing communications over the WAN1454, such as by way of the Internet. The modem 1458, which can beinternal or external and a wired or wireless device, is connected to thesystem bus 1408 via the serial port interface 1442. In a networkedenvironment, program modules depicted relative to the computer 1402, orportions thereof, can be stored in the remote memory/storage device1450. It will be appreciated that the network connections shown areexemplary and other means of establishing a communications link betweenthe computers can be used.

The computer 1402 is operable to communicate with any wireless devicesor entities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, any piece of equipment or locationassociated with a wirelessly detectable tag (e.g., a kiosk, news stand,restroom), and telephone. This includes at least Wi-Fi and Bluetooth™wireless technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi, or Wireless Fidelity, allows connection to the Internet from acouch at home, a bed in a hotel room, or a conference room at work,without wires. Wi-Fi is a wireless technology similar to that used in acell phone that enables such devices, e.g., computers, to send andreceive data indoors and out; anywhere within the range of a basestation. Wi-Fi networks use radio technologies called IEEE802.11 (a, b,g, n, etc.) to provide secure, reliable, fast wireless connectivity. AWi-Fi network can be used to connect computers to each other, to theInternet, and to wired networks (which use IEEE802.3 or Ethernet). Wi-Finetworks operate in the unlicensed 2.4 and 5 GHz radio bands, at an 14Mbps (802.11b) or 54 Mbps (802.11a) data rate, for example, or withproducts that contain both bands (dual band), so the networks canprovide real-world performance similar to the basic “10BaseT” wiredEthernet networks used in many offices.

What has been described above includes examples of the variousembodiments. It is, of course, not possible to describe everyconceivable combination of components or methodologies for purposes ofdescribing the embodiments, but one of ordinary skill in the art mayrecognize that many further combinations and permutations are possible.Accordingly, the detailed description is intended to embrace all suchalterations, modifications, and variations that fall within the spiritand scope of the appended claims.

As used in this application, the terms “system,” “component,”“interface,” and the like are generally intended to refer to acomputer-related entity or an entity related to an operational machinewith one or more specific functionalities. The entities disclosed hereincan be either hardware, a combination of hardware and software,software, or software in execution. For example, a component may be, butis not limited to being, a process running on a processor, a processor,an object, an executable, a thread of execution, a program, and/or acomputer. By way of illustration, both an application running on aserver and the server can be a component. One or more components mayreside within a process and/or thread of execution and a component maybe localized on one computer and/or distributed between two or morecomputers. These components also can execute from various computerreadable storage media having various data structures stored thereon.The components may communicate via local and/or remote processes such asin accordance with a signal having one or more data packets (e.g., datafrom one component interacting with another component in a local system,distributed system, and/or across a network such as the Internet withother systems via the signal). As another example, a component can be anapparatus with specific functionality provided by mechanical partsoperated by electric or electronic circuitry that is operated bysoftware or firmware application(s) executed by a processor, wherein theprocessor can be internal or external to the apparatus and executes atleast a part of the software or firmware application. As yet anotherexample, a component can be an apparatus that provides specificfunctionality through electronic components without mechanical parts,the electronic components can include a processor therein to executesoftware or firmware that confers at least in part the functionality ofthe electronic components. An interface can include input/output (I/O)components as well as associated processor, application, and/or APIcomponents.

Furthermore, the disclosed subject matter may be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques to produce software, firmware, hardware,or any combination thereof to control a computer to implement thedisclosed subject matter. The term “article of manufacture” as usedherein is intended to encompass a computer program accessible from by acomputing device.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor also can be implemented as acombination of computing processing units.

In the subject specification, terms such as “store,” “data store,” “datastorage,” “database,” “repository,” “queue”, and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory. In addition, memory components or memory elementscan be removable or stationary. Moreover, memory can be internal orexternal to a device or component, or removable or stationary. Memorycan include various types of media that are readable by a computer, suchas hard-disc drives, zip drives, magnetic cassettes, flash memory cardsor other types of memory cards, cartridges, or the like.

By way of illustration, and not limitation, nonvolatile memory caninclude read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable ROM (EEPROM), or flashmemory. Volatile memory can include random access memory (RAM), whichacts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), anddirect Rambus RAM (DRRAM). Additionally, the disclosed memory componentsof systems or methods herein are intended to comprise, without beinglimited to comprising, these and any other suitable types of memory.

In particular and in regard to the various functions performed by theabove described components, devices, circuits, systems and the like, theterms (including a reference to a “means”) used to describe suchcomponents are intended to correspond, unless otherwise indicated, toany component which performs the specified function of the describedcomponent (e.g., a functional equivalent), even though not structurallyequivalent to the disclosed structure, which performs the function inthe herein illustrated exemplary aspects of the embodiments. In thisregard, it will also be recognized that the embodiments includes asystem as well as a computer-readable medium having computer-executableinstructions for performing the acts and/or events of the variousmethods.

Computing devices typically include a variety of media, which caninclude computer-readable storage media and/or communications media,which two terms are used herein differently from one another as follows.Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disk (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or other tangible and/or non-transitorymedia which can be used to store desired information. Computer-readablestorage media can be accessed by one or more local or remote computingdevices, e.g., via access requests, queries or other data retrievalprotocols, for a variety of operations with respect to the informationstored by the medium.

On the other hand, communications media typically embodycomputer-readable instructions, data structures, program modules orother structured or unstructured data in a data signal such as amodulated data signal, e.g., a carrier wave or other transportmechanism, and includes any information delivery or transport media. Theterm “modulated data signal” or signals refers to a signal that has oneor more of its characteristics set or changed in such a manner as toencode information in one or more signals. By way of example, and notlimitation, communications media include wired media, such as a wirednetwork or direct-wired connection, and wireless media such as acoustic,RF, infrared and other wireless media

Further, terms like “user equipment,” “user device,” “mobile device,”“mobile,” station,” “access terminal,” “terminal,” “handset,” andsimilar terminology, generally refer to a wireless device utilized by asubscriber or user of a wireless communication network or service toreceive or convey data, control, voice, video, sound, gaming, orsubstantially any data-stream or signaling-stream. The foregoing termsare utilized interchangeably in the subject specification and relateddrawings. Likewise, the terms “access point,” “node B,” “base station,”“evolved Node B,” “cell,” “cell site,” and the like, can be utilizedinterchangeably in the subject application, and refer to a wirelessnetwork component or appliance that serves and receives data, control,voice, video, sound, gaming, or substantially any data-stream orsignaling-stream from a set of subscriber stations. Data and signalingstreams can be packetized or frame-based flows. It is noted that in thesubject specification and drawings, context or explicit distinctionprovides differentiation with respect to access points or base stationsthat serve and receive data from a mobile device in an outdoorenvironment, and access points or base stations that operate in aconfined, primarily indoor environment overlaid in an outdoor coveragearea. Data and signaling streams can be packetized or frame-based flows.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,” andthe like are employed interchangeably throughout the subjectspecification, unless context warrants particular distinction(s) amongthe terms. It should be appreciated that such terms can refer to humanentities, associated devices, or automated components supported throughartificial intelligence (e.g., a capacity to make inference based oncomplex mathematical formalisms) which can provide simulated vision,sound recognition and so forth. In addition, the terms “wirelessnetwork” and “network” are used interchangeable in the subjectapplication, when context wherein the term is utilized warrantsdistinction for clarity purposes such distinction is made explicit.

Moreover, the word “exemplary” is used herein to mean serving as anexample, instance, or illustration. Any aspect or design describedherein as “exemplary” is not necessarily to be construed as preferred oradvantageous over other aspects or designs. Rather, use of the wordexemplary is intended to present concepts in a concrete fashion. As usedin this application, the term “or” is intended to mean an inclusive “or”rather than an exclusive “or”. That is, unless specified otherwise, orclear from context, “X employs A or B” is intended to mean any of thenatural inclusive permutations. That is, if X employs A; X employs B; orX employs both A and B, then “X employs A or B” is satisfied under anyof the foregoing instances. In addition, the articles “a” and “an” asused in this application and the appended claims should generally beconstrued to mean “one or more” unless specified otherwise or clear fromcontext to be directed to a singular form.

In addition, while a particular feature may have been disclosed withrespect to only one of several implementations, such feature may becombined with one or more other features of the other implementations asmay be desired and advantageous for any given or particular application.Furthermore, to the extent that the terms “includes” and “including” andvariants thereof are used in either the detailed description or theclaims, these terms are intended to be inclusive in a manner similar tothe term “comprising.”

What is claimed is:
 1. A device, comprising: a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: determiningthat a first access point device serves a user equipment via a firstcommunication path between the first access point device and the userequipment, wherein the first access point device serves the userequipment according to a first protocol representing a third generationpartnership project protocol; determining that a second access pointdevice serves the user equipment via a second communication path betweenthe second access point device and the user equipment, wherein thesecond access point device serves the user equipment according to asecond protocol representing a non-third generation partnership projectprotocol; receiving an indication that a secure tunnel has beenestablished according to the first protocol between the first accesspoint device and the second access point device, wherein the receivingthe indication is in response to the secure tunnel having beenestablished, wherein the secure tunnel was established in response todetermining that a condition has been satisfied, and wherein thecondition comprises that the first access point device and the secondaccess point device have been determined to be co-located; andcommunicating data via a virtual tunnel that traverses the second accesspoint device that serves the user equipment according to the secondprotocol representing the non-third generation partnership projectprotocol, the first access point device that is co-located with thesecond access point device and serves the user equipment according tothe first protocol representing the third generation partnership projectprotocol, and the secure tunnel, wherein the virtual tunnel isdesignated to correspond to a bearer specified by the first protocol. 2.The device of claim 1, wherein the first protocol is a long-termevolution protocol and wherein the second protocol is a wirelessfidelity protocol.
 3. The device of claim 1, wherein the device isselected from a group comprising: the first access point device, thesecond access point device, and the user equipment.
 4. The device ofclaim 1, wherein the data comprises uplink data communicated from theuser equipment to a network device, and wherein the communicating thedata comprises one from a group comprising: transmitting the uplink dataand receiving the uplink data.
 5. The device of claim 1, wherein thedata comprises downlink data communicated from a network device to theuser equipment, and wherein the communicating the data comprises onefrom a group comprising: transmitting the downlink data and receivingthe downlink data.
 6. The device of claim 1, wherein the first accesspoint device and the second access point device were determined to beco-located in response to a determination that the first access pointdevice and the second access point device are physically co-located andexist in a common physical structure.
 7. The device of claim 1, whereinthe first access point device and the second access point device weredetermined to be co-located in response to a determination that thefirst access point device and the second access point device aretopologically co-located with respect to a defined network topology. 8.The device of claim 1, wherein the first communication path comprisesbearers, comprising the bearer, that are representative of first virtualcommunication paths specified by the first protocol, and wherein thesecond communication path comprises links representative of secondvirtual communication paths.
 9. The device of claim 8, wherein theoperations further comprise determining translation data representativeof a logical mapping between the links, relating to communication viathe second protocol, and the bearers, relating to communication via thefirst protocol.
 10. The device of claim 9, wherein the translation datacomprises: first tunnel data representative of a first logical mappingbetween a first link of the links and a radio bearer of the bearersspecified by the first protocol to represent a first tunnel between theuser equipment and the first access point device; second tunnel datarepresentative of a second logical mapping between a second link of thelinks and an evolved radio access bearer of the bearers specified by thefirst protocol to represent a second tunnel between the user equipmentand a serving gateway device; and third tunnel data representative of athird logical mapping between a third link of the links and an evolvedpacket system bearer of the bearers specified by the first protocol torepresent a third tunnel between the user equipment and a packet datanetwork gateway device.
 11. A machine-readable storage medium,comprising executable instructions that, when executed by a processor,facilitate performance of operations, comprising: determining that afirst access point device serves a user equipment via a firstcommunication path between the first access point device and the userequipment, wherein the first access point device serves the userequipment according to a first protocol representative of a cellularprotocol defined by third generation partnership project; determiningthat a second access point device serves the user equipment via a secondcommunication path between the second access point device and the userequipment, wherein the second access point device serves the userequipment according to a second protocol representative of a wirelessprotocol not defined by the third generation partnership project;receiving an indication that, according to the first protocol, a securetunnel has been established between the first access point device andthe second access point device, wherein the receiving the indication isin response to the secure tunnel being established, wherein the securetunnel is established in response to a condition being determined tohave been satisfied, and wherein the condition that is determined tohave been satisfied is that the first access point device and the secondaccess point device have been determined to be co-located; andcommunicating data via a virtual tunnel that traverses the second accesspoint device that serves the user equipment according to the secondprotocol, the first access point device that is co-located with thesecond access point device and that serves the user equipment accordingto the first protocol, and the secure tunnel, and that is designated tocorrespond to a bearer described by the first protocol.
 12. Themachine-readable storage medium of claim 11, wherein the first protocolrepresents a long-term evolution protocol and wherein the secondprotocol is a wireless fidelity protocol.
 13. The machine-readablestorage medium of claim 11, wherein the condition is determined to havebeen satisfied in response to a determination that the first accesspoint device and the second access point device are physicallyco-located and situated in a common physical structure.
 14. Themachine-readable storage medium of claim 11, wherein the condition isdetermined to have been satisfied in response to a determination thatthe first access point device and the second access point device aretopologically co-located with respect to a defined network topology. 15.The machine-readable storage medium of claim 11, wherein the firstcommunication path comprises bearers, comprising the bearer, that arerepresentative of first virtual communication paths specified by thefirst protocol, and wherein the second communication path compriseslinks representative of second virtual communication paths.
 16. Themachine-readable storage medium of claim 15, wherein the operationsfurther comprise determining mapping data representative of a logicalmapping between the bearers, relating to communication via the firstprotocol, and the links, relating to communication via the secondprotocol.
 17. A method, comprising: determining, by a system comprisinga processor, that a first access point device serves a user equipmentvia a first communication path between the first access point device andthe user equipment, wherein the first access point device serves theuser equipment according to a first protocol indicative of acellular-based protocol specified by a third generation partnershipproject specification; determining, by the system, that a second accesspoint device serves the user equipment via a second communication pathbetween the second access point device and the user equipment, whereinthe second access point device serves the user equipment according to asecond protocol indicative of a wireless-based protocol that differsfrom the cellular-based protocol; determining, by the system, that asecure tunnel was established in response to a condition manifesting,wherein the secure tunnel was established, according to the firstprotocol, between the first access point device and the second accesspoint device, and wherein the condition manifesting comprises the firstaccess point device and the second access point device being determinedto be co-located; and communicating, by the system, data via a virtualtunnel that traverses the second access point device that serves theuser equipment according to the second protocol, the first access pointdevice that is co-located with the second access point device and thatserves the user equipment according to the first protocol, and thesecure tunnel, and is designated to correspond to a bearer dictated bythe first protocol.
 18. The method of claim 17, wherein thecommunicating the data comprises a member of a group comprising:transmitting data from the user equipment device and transmitting datato the user equipment device.
 19. The method of claim 17, wherein thefirst access point device and the second access point device aredetermined to be co-located based on a determination that the firstaccess point device and the second access point device are physicallyco-located and situated in a common physical structure.
 20. The methodof claim 17, wherein the first access point device and the second accesspoint device are determined to be co-located based on a determinationthat the first access point device and the second access point deviceare topologically co-located with respect to a defined network topology.